[PATCH] Correctly handle signed 32-bit time_t types
authorNoah Meyerhans <noahm@debian.org>
Wed, 4 Feb 2026 16:09:21 +0000 (11:09 -0500)
committerNoah Meyerhans <noahm@debian.org>
Wed, 4 Feb 2026 16:09:21 +0000 (11:09 -0500)
commit1ab315beec3ee80d673fabf9be2fc6cc927fad63
treee187e3d2f6657e6267ded558e4e1a6bb32b08864
parent7bde382b8481dbf1a16359683004d332efcd2e27
[PATCH] Correctly handle signed 32-bit time_t types

Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1124541
Forwarded: no

dovecot handles 32-bit time_t in a couple of different ways, but neither quite
works currently.  Setting TIME_T_MAX_BITS to 31 isn't correctly handled in
places where time_t values are constructed, for example in
io_loop_get_wait_time().

Similarly, setting TIME_T_MAX_BITS = 32 and defining TIME_T_SIGNED is not
correctly handled by tm_is_too_large().

This change fixes tm_is_too_large() to set max_time to the correct maximum date
representable by a signed 32-bit time_t.

Closes: #1124541
Gbp-Pq: Name Correctly_handle_signed_32-bit_time_t_types.patch
src/lib-imap/imap-date.c
src/lib-imap/test-imap-date.c